Skip to content

Conversation

@harshavamsi
Copy link
Contributor

Description

As described in #19636, we check the bounds of the ordinal before we seek

Related Issues

Resolves #19636

Check List

  • Functionality includes testing.
  • API changes companion pull request created, if applicable.
  • Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@harshavamsi
Copy link
Contributor Author

@msfroh could you take a look since you added this optimization

Signed-off-by: Harsha Vamsi Kalluri <[email protected]>
@harshavamsi harshavamsi force-pushed the fix-prefix-ordinals-index-out-of-bounds branch from e90ffb1 to 7f1e867 Compare October 14, 2025 19:48
@harshavamsi harshavamsi added the v3.4.0 Issues and PRs related to version 3.4.0 label Oct 14, 2025
Copy link
Contributor

@msfroh msfroh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this!

@github-actions
Copy link
Contributor

❌ Gradle check result for 7f1e867: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@harshavamsi harshavamsi reopened this Oct 14, 2025
@github-actions
Copy link
Contributor

✅ Gradle check result for 7d81d75: SUCCESS

Copy link
Contributor

@jainankitk jainankitk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@github-project-automation github-project-automation bot moved this from In-Review to In Progress in Performance Roadmap Oct 24, 2025
@github-actions
Copy link
Contributor

✅ Gradle check result for 2077e9e: SUCCESS

@github-actions
Copy link
Contributor

❌ Gradle check result for d6eb8db: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@jainankitk
Copy link
Contributor

Another flaky test:

[Test Result](https://build.ci.opensearch.org/job/gradle-check/66323/testReport/) (1 failure / +1)

    [org.opensearch.action.admin.cluster.node.tasks.ResourceAwareTasksTests.testTaskResourceTrackingDuringTaskCancellation](https://build.ci.opensearch.org/job/gradle-check/66323/testReport/junit/org.opensearch.action.admin.cluster.node.tasks/ResourceAwareTasksTests/testTaskResourceTrackingDuringTaskCancellation/)

cc: @kaushalmahi12 / @ruai0511

@github-actions
Copy link
Contributor

✅ Gradle check result for d6eb8db: SUCCESS

@jainankitk jainankitk merged commit 09b3b96 into opensearch-project:main Oct 28, 2025
35 of 39 checks passed
@github-project-automation github-project-automation bot moved this from In Progress to Done in Performance Roadmap Oct 28, 2025
@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.x
# Create a new branch
git switch --create backport/backport-19637-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 09b3b962cdbb703591fe7422f6eecad541f89c45
# Push it to GitHub
git push --set-upstream origin backport/backport-19637-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-19637-to-2.x.

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.19 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.19 2.19
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.19
# Create a new branch
git switch --create backport/backport-19637-to-2.19
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 09b3b962cdbb703591fe7422f6eecad541f89c45
# Push it to GitHub
git push --set-upstream origin backport/backport-19637-to-2.19
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.19

Then, create a pull request where the base branch is 2.19 and the compare/head branch is backport/backport-19637-to-2.19.

@opensearch-trigger-bot
Copy link
Contributor

The backport to 3.3 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-3.3 3.3
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-3.3
# Create a new branch
git switch --create backport/backport-19637-to-3.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 09b3b962cdbb703591fe7422f6eecad541f89c45
# Push it to GitHub
git push --set-upstream origin backport/backport-19637-to-3.3
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-3.3

Then, create a pull request where the base branch is 3.3 and the compare/head branch is backport/backport-19637-to-3.3.

@jainankitk jainankitk removed the backport 2.x Backport to 2.x branch label Oct 28, 2025
jainankitk added a commit that referenced this pull request Oct 28, 2025
…xistent prefix term (#19637)

Signed-off-by: Harsha Vamsi Kalluri <[email protected]>
Signed-off-by: Ankit Jain <[email protected]>
Co-authored-by: Ankit Jain <[email protected]>
(cherry picked from commit 09b3b96)
jainankitk added a commit that referenced this pull request Oct 28, 2025
…xistent prefix term (#19637)

Signed-off-by: Harsha Vamsi Kalluri <[email protected]>
Signed-off-by: Ankit Jain <[email protected]>
Co-authored-by: Ankit Jain <[email protected]>
(cherry picked from commit 09b3b96)
@jainankitk
Copy link
Contributor

Created the backport PRs for 2.19 and 3.3. Don't need to backport for 2.x as we don't expect to release off that branch anymore.

jainankitk added a commit that referenced this pull request Oct 28, 2025
…xistent prefix term (#19637) (#19792)

(cherry picked from commit 09b3b96)

Signed-off-by: Harsha Vamsi Kalluri <[email protected]>
Signed-off-by: Ankit Jain <[email protected]>
Co-authored-by: Harsha Vamsi Kalluri <[email protected]>
anandpatel9998 pushed a commit to anandpatel9998/OpenSearch that referenced this pull request Nov 3, 2025
…xistent prefix term (opensearch-project#19637)

Signed-off-by: Harsha Vamsi Kalluri <[email protected]>
Signed-off-by: Ankit Jain <[email protected]>
Co-authored-by: Ankit Jain <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport 2.19 backport 3.3 Backport to 3.3 branch backport-failed bug Something isn't working _No response_ Search:Resiliency v3.4.0 Issues and PRs related to version 3.4.0

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

[BUG] Include/Exclude on terms aggregation can cause IndexOutOfBoundsException

4 participants